Latency-based routing and load balancing in a network

ABSTRACT

Aspects of the disclosure relate to routing queries to a network repository and load balancing in a network. For a network repository having a plurality of content storage sites, relative replication latency of data among a pair of content storages sites can be monitored. Data indicative of such replication latency can be distributed among the content storage sites and can be provided, for example, to a network node in a system layer. A traffic and control manager can determine routing pathways for queries based at least in part on the relative replication latency data and performance conditions of network nodes.

CROSS REFERENCE TO RELATED PATENT APPLICATION

This application is a continuation of U.S. application Ser. No.14/755,731 filed Jun. 30, 2015, which is a continuation of U.S.application Ser. No. 13/363,996 filed Feb. 1, 2012 and issued as U.S.Pat. No. 9,106,663, which are herein incorporated by reference in theirentireties.

BACKGROUND

Architectures for administration of network systems become more complexas networks increase in size and functionality (e.g., availableservices, integration with sub-systems and other networks, and thelike). In addition to complexity, operational requirements foradministration of such systems also tend to increase. In response,backend architectures commonly incorporate active/active replicationtopologies. Such topologies can comprise multiple master applicationfootprints having, for example, asynchronous replication data betweeneach master node in the active replication topology. Typically, themaster nodes can convey (e.g., broadcast, unicast, or multicast) changesto other nodes in the active replication topology and can subscribe toreceive changes that occur in other master nodes.

SUMMARY

The disclosure relates, in one aspect, to routing queries (e.g., contentqueries, service queries) to a network repository (e.g., a distributedcontent repository) and balancing load in a network having or beingcoupled to such repository. For a network repository (e.g., a datalayer) having a plurality of content storage sites configured in acontent replication topology, relative replication latency of contentamong each pair of content storage sites in the plurality of contentstorage sites can be monitored in accordance with various monitoringprotocols, e.g., nearly continuous monitoring, periodic monitoring,scheduled monitoring, event-triggered monitoring, or the like. Suchmonitoring can update replication latency information at the contentstorage sites. Such sites can be referred to as nodes or end points andcan comprise source nodes, which can supply content updates and relatedchanges to a content replica, and target nodes, which can receive suchcontent updates. Based at least in part on, for example, contentupdates, data indicative of replication latency can be distributed(e.g., broadcast, multicast, unicast, or the like) among the contentstorage sites and can be provided, for example, to a network node in abackend system layer, such as an application layer. Such data also canbe persisted in a memory element (registers, memory pages, files,databases, etc.) of each content storage site in the data layer. Toprovide data indicative of replication latency among end points, eachcontent storage site can implement control signaling, such as signalingbeats, between all source nodes and target nodes (also referred to assubscribers) and can call a publisher node (also referred to as source)to inform (or update) replication latencies at respective targets.

In another aspect, the data indicative of relative replication latencycan permit, at least in part, automated routing of queries (e.g.,content queries) in response to performance conditions of a networknode. In one scenario, for example, a traffic and control manager unit(e.g., a router or a load balancer) in the backend system layer candetermine routing pathways for queries based at least in part on therelative replication latency data and performance conditions of networknodes in the backend system layer.

Some embodiments of the disclosure provide various advantages whencompared to conventional technologies for routing traffic in an activereplication topology. For example, some embodiments can provide routingcriteria based at least on relative replication latency and performanceconditions, and can permit automated determination of routing pathwaysfor content queries and, more generally, traffic.

Additional aspects or advantages of the subject disclosure will be setforth in part in the description which follows, and in part will beobvious from the description, or may be learned by practice of thesubject disclosure. The advantages of the subject disclosure will berealized and attained by means of the elements and combinationsparticularly pointed out in the appended claims. It is to be understoodthat both the foregoing general description and the following detaileddescription are exemplary and explanatory only and are not restrictiveof the subject disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The annexed drawings are an integral part of the subject disclosure andillustrate exemplary embodiments thereof. Together with the descriptionset forth herein and the claims appended hereto, the annexed drawingsserve to explain various principles, features, or aspects of the subjectdisclosure.

FIG. 1 illustrates an exemplary network environment in accordance withone or more aspects of the disclosure.

FIG. 2 illustrates an exemplary embodiment of a multi-layer networksystem in accordance with one or more aspects described herein.

FIG. 3 illustrates an exemplary configuration of content storage inaccordance with one or more aspects of the disclosure.

FIG. 4 illustrates exemplary embodiments of content storage andexemplary configuration thereof in accordance with one or more aspectsof the disclosure.

FIG. 5 illustrates an exemplary network node in accordance with one ormore aspects of the disclosure.

FIG. 6 illustrates an exemplary computing device in accordance with oneor more aspects of the disclosure.

FIG. 7 illustrates an exemplary data manager in accordance with one ormore aspects of the disclosure.

FIG. 8 illustrates an exemplary method in accordance with one or moreaspects of the disclosure.

FIG. 9A illustrates an exemplary method in accordance with one or moreaspects of the disclosure.

FIG. 9B illustrates an exemplary method in accordance with one or moreaspects of the disclosure.

DETAILED DESCRIPTION

The various aspects described herein can be understood more readily byreference to the following detailed description of exemplary embodimentsof the subject disclosure and to the annexed drawings and their previousand following description.

Before the present systems, articles, apparatuses, and methods aredisclosed and described, it is to be understood that the subjectdisclosure is not limited to specific systems, articles, apparatuses,and methods for integrating information related to replication latencyamong network nodes into routing of queries (e.g., content queries,service queries) in an active replication topology of a distributedcontent repository. It is also to be understood that the terminologyemployed herein is for the purpose of describing particular,non-exclusive embodiments only and is not intended to be limiting.

As used in the specification and the appended claims, the singular forms“a,” “an” and “the” include plural referents unless the context clearlydictates otherwise. Ranges may be expressed herein as from “about” oneparticular value, and/or to “about” another particular value. When sucha range is expressed, another embodiment includes from the oneparticular value and/or to the other particular value. Similarly, whenvalues are expressed as approximations, by use of the antecedent“about,” it will be understood that the particular value forms anotherembodiment. It will be further understood that the endpoints of each ofthe ranges are significant both in relation to the other endpoint, andindependently of the other endpoint.

As utilized in this specification and the annexed drawings, the terms“system,” “layer,” “component,” “unit,” “interface,” “platform,” “node,”“function” and the like are intended to include a computer-relatedentity or an entity related to an operational apparatus with one or morespecific functionalities, wherein the computer-related entity or theentity related to the operational apparatus can be either hardware, acombination of hardware and software, software, or software inexecution. Such entities also are referred to as “functional elements.”As an example, a unit can be, but is not limited to being, a processrunning on a processor, a processor, an object (metadata object, dataobject, signaling object), an executable computer program, a thread ofexecution, a program, a memory (e.g., a hard-disc drive), and/or acomputer. As another example, a unit can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry which is operated by a software application or afirmware application executed by a processor, wherein the processor canbe internal or external to the apparatus and can execute at least aportion of the software application or the firmware application. As yetanother example, a unit can be an apparatus that provides specificfunctionality through electronic functional elements without mechanicalparts, the electronic functional elements can include a processortherein to execute software or firmware that provides, at least in part,the functionality of the electronic functional elements. The foregoingexamples and related illustrations are but a few examples and are notintended to be limiting. In addition, while such illustrations arepresented for a unit, the foregoing examples also apply to a system, alayer, a node, an interface, a function, a component, a platform, andthe like. It is noted that in certain embodiments, or in connection withcertain aspects or features such embodiments, the terms “system,”“layer,” “unit,” “component,” “interface,” “platform” “node,” “function”can be utilized interchangeably.

Throughout the description and claims of this specification, the words“comprise,” “include,” and “having” and their variations, such as“comprising” and “comprises,” “include” and “including.” “having” and“has,” mean “including but not limited to,” and are not intended toexclude, for example, other units, nodes, components, functions,interfaces, actions, steps, or the like. “Exemplary” means “an exampleof” and is not intended to convey an indication of a preferred or idealembodiment. “Such as” is not used in a restrictive sense, but forexplanatory purposes.

Reference will now be made in detail to the various embodiments andrelated aspects of the subject disclosure, examples of which areillustrated in the accompanying drawings and their previous andfollowing description. Wherever possible, the same reference numbers areused throughout the drawings to refer to the same or like parts.

The disclosure identifies and addresses, in one aspect, the lack of datareplication latency associated with instantiation of content changesamong network nodes in a replication topology, and implications of suchlack of knowledge in routing of traffic and/or signaling to adistributed content repository. As described in greater detail below, inone aspect, the disclosure relates to routing queries (e.g., contentqueries, service queries) to a network repository (e.g., a distributedcontent repository) and balancing load in a network having or beingcoupled to such repository. For a network repository having a pluralityof content storage sites configured in an active replication topology,relative replication latency of content (e.g., data and/or metadata)among each pair of content storages sites in the plurality of contentstorage sites can be monitored (nearly continuously, periodically, atscheduled instants, in response to an event, etc.). Data indicative ofsuch replication latency can be distributed among the content storagesites and can be provided, for example, to a network node in a layer ofa backend system, such as an application layer. A traffic and controlmanager unit (e.g., a router or a load balancer) in the layer of thebackend system can determine routing pathways for queries based at leastin part on the relative replication latency data and performanceconditions of network nodes in the application layer. In addition or inthe alternative, the traffic and control manager unit can balance load(e.g., volume of queries) of a network node based on performancecondition of such node. Certain functional elements of the subjectdisclosure can be implemented (e.g., performed) by software, hardware,or a combination of software and hardware. Functional elements of thevarious embodiments described in the present specification andillustrated in the annexed drawings can be employed in operationalenvironments (access network, telecommunication network, signalingnetwork, etc.) that can include, for example, digital equipment, analogequipment, or both, wired or wireless equipment, etc.

FIG. 1 is a high-level block diagram of an exemplary network environment100 in accordance with one or more aspects of the disclosure. Asillustrated, the exemplary network environment 100 comprises a network110 functionally coupled (e.g., communicatively coupled via wired linksor wireless links, or a combination thereof) to a backend system 120. Incertain embodiments, the network 110 can be a service network. Suchcoupling permits, at least in part, the network 110 to provide aservice. A data and signaling pipe 114 comprising an upstream link, oruplink (UL), and a downstream link, or downlink (DL), enables functionalcoupling among the backend system 120 and the network 110. The UL isrepresented with an arrow oriented outwards from the network 110,whereas the DL is represented with an arrow oriented towards the network110. The data and signaling pipe 114 can comprise one or more of: areference link (Cx, Cr, Dh, Dx, Gm, Ma, Mg, or the like) and relatedcomponents; conventional bus architectures such as address buses, systembuses; wired links, such as fiber optic lines, coaxial lines, hybridfiber-coaxial links, Ethernet lines, T-carrier lines, twisted-pair line,or the like, and various connectors (e.g., an Ethernet connector, an Fconnector, an RS-232 connector, or the like); wireless links, includingterrestrial wireless links, satellite-based wireless links, or acombination thereof; and so forth.

The network 110 can include wireless networks, wire line networks, or acombination thereof, and can provide a service to one or more devices,such as user equipment, customer premises equipment, control equipment(e.g., signaling units), operation and maintenance (O&M) equipment(e.g., network probes), and the like. In one aspect, the serviceprovided by the network 110 can be a consumer service, such as contentcommunication (media on demand, Internet service, digital telephony(e.g., voice over internet protocol (VoIP)), multimedia message service(MMS), short message service (SMS), etc.); content management (e.g.,network digital video recording, messaging administration); emergencyservices (e.g., enhanced 911); location-based services; or the like. Inanother aspect, the service provided by the network 110 can be a networkadministration service, which can comprise one or more of accounting andbilling, access control, subscriber provisioning, customer servicesupport (including, for example, interactive voice response (IVR)),performance monitoring (e.g., dashboard services, automation control,etc.), or the like. Architecture of the network 110 can be specific tothe provided service.

The network 110 can embody or comprise one or more of a wide areanetwork (WAN), a signaling network (e.g., SS#7), an enterprise network,a local area network, a home area network, a personal area network(which can include wearable devices), or the like. Such networks canoperate in accordance with one or more communication protocols for wireline communication or wireless communication. In certain embodiments,the network 110 can have several functional elements that can provide abackbone network, such as a high-capacity packet-switched network. Inother embodiments, the network 110 can have internal structure, withseveral functional elements that can provide at least two mainoperational blocks: a backbone network (e.g., a high-capacitypacket-switched network) and a regional access network (RAN). Theinternal structure also can include functional elements that providemore spatially localized networks, such as local area networks, homearea networks, or the like. Both the backbone network and the regionalaccess network (RAN) can be WANs, for example, with the backbone networkhaving a larger geographical scope than the RAN.

The backend system 120 can comprise an application layer 130 which canprovide specific functionality associated with a service (consumerservice, enterprise service, network administration, etc.) of thenetwork 110. The application layer 130 can be configured as a singlelogical unit and can comprise one or more application servers that canimplement (e.g., execute) such functionality. An application server canbe, for example, a content server for pay-per-view programming orvideo-on-demand assets, an application server (e.g., an email server), adata server, a telephony server, a backbone network router, or the like.In network management scenarios, an application server can comprise anaccess request manager server, a provisioning server, an accountingserver, and a billing record collector server. In one embodiment, theaccess request manager server can comprise an authentication,authorization, and account (AAA) server, which can implement one or moreaccess protocols (Kerberos, RADIUS, Diameter, lightweight directoryaccess protocol (LDAP), etc.), and access control unit (or accesscontroller), the provisioning server can be a dynamic host configurationprotocol (DHCP) engine; and the billing record collector server can bean IP detail record (IPDR) collector server. In addition or in thealternative, the application layer 130 can comprise one or more networknodes, such as utility servers, routers (e.g., broadband remote accessserver (BRAS)), or network switches (e.g., digital subscriber lineaccess multiplexer (DSLAM)), that can provide utility functions to theapplication layer 130. As an illustration, a utility server can be a webserver that can permit, at least in part, access to web services and tocommunication based on various web-based communication protocols, suchas hypertext transfer protocol (HTTP), simple object access protocol(SOAP), or simple network management protocol (SNMP). In one embodiment,e.g., exemplary embodiment 200 shown in FIG. 2, the application layer130 can include P servers 214 ₁-214 _(P), with P a natural number equalto or greater than unity, and a traffic and control manager unit 224(also referred to as traffic and control manager 224). Functionality andarchitecture of each one of servers 214 ₁-214 _(P) can be specific tothe embodiment of the backend system 120. At least one server (e.g.,one, a combination of two, or a combination of more than two) of theservers 214 ₁-214 _(P) can be functionally coupled to a traffic andcontrol (T&C) manager unit 224 (also referred to herein as T&C manager224). Each one of the servers 214 ₁-214 _(P) can be coupled can befunctionally coupled to the T&C manager 224 via a respective data andsignaling pipe 220 _(κ). Here, κ is an index that adopts values from 1to P at intervals of 1, e.g., κ=1, 2 . . . P. Each one of the data andsignaling pipes 220 ₁-220 _(P) can include one or more of wirelesslinks, wire line links, or a combination thereof. Each of such data andsignaling pipes can comprise one or more of: a reference link (Cx, Cr,Dh, Dx, Gm, Ma, Mg, or the like) and related components; conventionalbus architectures such as address buses, system buses; wired links, suchas fiber optic lines, coaxial lines, hybrid fiber-coaxial links,Ethernet lines, T-carrier lines, twisted-pair line, or the like, andvarious connectors (e.g., Ethernet connectors, F connectors, RS-232connectors, or the like); wireless links, including terrestrial wirelesslinks, satellite-based wireless links, or a combination thereof; and soforth.

The application layer 130 can receive a query 118 from the network 110or a component thereof. Such network can transmit the query 118 as partof providing a service. In one aspect, a traffic and control manager 224can receive the query 118. In one aspect, the query 118 can requestcontent (data, metadata, etc.) specific to the service. In addition orin the alternative, the query 118 can request an update of specific datarelated to the service. The application layer 130, via the traffic andcontrol manager 224, for example, can process the query 118. As part ofthe processing, in one aspect, the application layer 130 can generate anupdated query. The traffic and control manager 224 can determine apathway for routing the query 118 or the processed query to a contentrepository 150 in which a functional element (e.g., a database managerunit) can process the query 118 or the updated query, or both, and cangenerate a response. In addition or in the alternative, the traffic andcontrol manager 224 can balance load (e.g., volume of queries) of aserver of the one or more servers 214 ₁-214 _(P) based at least onperformance condition(s) of the server.

As illustrated in exemplary environment 100, the content repository 150can comprise a group of one or more data layers 160. Each data layer canbe configured as a single logical unit having a plurality of contentstorage sites that can have content (data, metadata, etc.) suitable forgenerating a response to the query 118 or the processed query. In oneembodiment, e.g., embodiment 200, a data layer 240 of the group of oneor more data layers 160 can comprise a plurality of content storagesites 250 ₁-250 _(Q), with Q a natural number greater than unity. In oneaspect, each content storage site 250 _(ν) can be functionally coupledto the other Q−1 content storage sites 250 _(μ), via a data andsignaling pipe 254 _(νμ), which is identified with a pair of indicesthat represent the coupled content storage sites. Here, ν and μ areindices that each adopts values from 1 to Q at intervals of 1, e.g.,ν=1, 2 . . . Q and μ=1, 2 . . . Q, with the condition of μ≠ν. Inresponse to the query 118, a content storage site (e.g., content storagesite 250 ₂) in a data layer (e.g., data layer 240) in the group of oneor more layers 160 can transmit content (e.g., data or metadata) to theapplication layer 130 which can relay such content to the network 110.In one scenario, the content storage site can transmit the content to afunctional element (e.g., a server) of the application layer 130originating the query or processed query. In another scenario, thecontent can be transmitted to two or more functional elements (e.g., agateway and a server) in the application layer 130, the two or morefunctional elements can include the functional element originating thequery or the processed query.

Communication among a data layer of the one or more data layers 160 andthe application layer 130 can be accomplished, at least in part, viadata and signaling pipe 140. In one aspect, such communication can beeffected in accordance with one or more packet-switched protocols, suchas Ethernet protocol format; internet protocol (IP) format, such as IPv4and IPv6, or the like; TCP/IP, user datagram protocol (UDP) format,HTTP, simple object access protocol (SOAP), simple network managementprotocol (SNMP), or the like. Similarly to other data and signalingpipes described herein, the data and signaling pipe 140 can comprise oneor more of: a reference link and related components (routers, switches,gateways, interfaces, ports, connectors, etc.); conventional busarchitectures, such as address buses or system buses; wired links, suchas fiber optic lines, coaxial lines, hybrid fiber-coaxial links,Ethernet lines, T-carrier lines, twisted-pair line, or the like, andvarious connectors (e.g., Ethernet connectors, F connectors, RS-232connectors, or the like); wireless links, including terrestrial wirelesslinks, satellite-based wireless links, or a combination thereof; and soforth.

A server in the application layer 130 can be associated with a set ofone or more content storage sites that can supply data in response torequests from the server. In certain scenarios, the association amongthe server and the set of one or more content storage sites (e.g., 250₁-250 _(Q)) can be based on geopolitical considerations, wherein theserver can be assigned to a single content storage site servicing mostapplication servers deployed within a specific region. As illustrated inFIG. 3, in an exemplary deployment 300 of a data layer, a plurality ofcontent storage sites 320 ₁-320 ₆ can be distributed in certaingeopolitical area 310. Such content storage sites are functionallycoupled through data and signaling pipes represented with open-headarrows, to pictorially indicate that one or more network components(router(s), server(s), network switches(s), connector(s), hubs, etc.)can permit communication among the sites. Each one of the plurality ofcontent storage sites can be deployed in a location within thegeopolitical area 310 and can service queries (e.g., generate a responseto such queries) originating from network elements of the network 110 ina specific region (e.g., Region I, Region II, Region III, Region IV,Region V, or Region VI) of the geographical area 310. While six contentstorage sites 310 ₁-310 ₆ are illustrated within the geographical (orgeopolitical) area 310, other deployments are possible and contemplatedin the subject disclosure. In one aspect, a data layer can includecontent storage sites having content of certain type. As an example, thecontent can comprise billing records and other billing data, and thedata layer can be a billing data layer. As another example, the contentcan comprise safety records, and the data layer can be safety data layercompliant with one or more regulation such as the CommunicationsAssistance for Law Enforcement Act (CALEA). As yet another example, thecontent can comprise records of certain type of subscribers, such asmembers of a loyalty program or a premium service, and the data layercan be a provisioning data layer. In another aspect, a data layer caninclude content storage sites associated with a specific tier in ahierarchical data structure. In yet another aspect, a data layer caninclude content storage sites having data specific to certain functionalfeatures of the service provided by the network 110. For instance, ifthe network 110 is an industrial automation network, the content storagesites can comprise data pertaining to a plurality of programmable logiccontroller deployed in such network.

In exemplary embodiment 200, to generate a routing pathway of the query118, the T&C manager 224 can probe a performance condition of at leastone server (e.g., one, each one, two, more than two . . . ) of the groupof one or more servers 214 ₁-214 _(P), wherein the performance conditionindicates a level of performance to service the query 118. Likewise, tobalance load of a server, the T&C manager 224 probe the performancecondition(s) of the server. The performance condition can becharacterized by an indicator in a scale of performance conditions. Forexample, such scale can be have tiers such as “Satisfactory,” indicatinga server is capable of properly servicing the query 118; “At Risk,”indicating a server may be unable to properly service the query 118; and“Underperforming,” indicating a server is unable to service the query118. Other scales, finer or coarser, also can be defined and utilized.The routing pathway can include information (e.g., a logical address)indicative of a destination content storage site (e.g., content storagesite 3 250 ₃) suitable to service the query 118, and information (e.g.,a plurality of logical addresses) indicative of a sequence of functionalelements, or hops, of data and signaling pipe 140 that can be utilizedto transmit the query 118 from an originating server in the data layer150 to the destination content storage site.

In one aspect, a server 214 _(κ) can include a performance monitorcomponent 216, (also referred to as performance monitor 216 _(κ)) thatcan generate a performance metric indicative of a volume of extantqueries directed to the server 214 _(κ). In one implementation, togenerate the performance metric, the performance monitor 216, can access(e.g., pull) information indicative of idle thread counts, memoryutilization, and the like, and assign such information to be theperformance metric. In another implementation, the performance monitor216, can determine, based on information retained in a container for aJava Virtual Machine, for example, a number of timed-out queries or anumber of queued queries (e.g., queries transmitted for service to aserver), or a combination thereof, and can assign the performance metricto one of the determined quantities. The performance monitor component216 _(κ) can publish, or otherwise convey, an object identifier (e.g., aSNMP OID) that can point to, or convey an address of, a data structurecomprising the performance metric. The object identifier that ispublished or conveyed can be accessed by a functional element (a server,a router, a unit, etc.) in the network 110 to monitor performance of thebackend system 120. In the exemplary system 200, the T&C manager 224 canbe part of a network operation center (NOC) that is part of or isfunctionally coupled to one or more of operational support systems (OSS)or business support systems (BSS). In one embodiment, the T&C manager224 can comprise or be embodied in a router. In another embodiment, theT&C manager 224 can comprise or be embodied in a load balancer. In otherembodiments, the T&C manager 224 can comprise or be embodied in a routerand a load balancer.

By probing a performance condition, the T&C manager 224 can access(e.g., receive or retrieve) a performance metric associated with theperformance condition of a server that is probed. The T&C manager 224can configure automatically a specific content storage site to servicethe query 118 in response to the performance metric fulfilling aspecific performance criterion, such as the performance metric having apredetermined value (e.g., attaining a lower bound). Accordingly, theT&C manager 224 can balance load in the application layer 150 inresponse to the performance condition, or state, of each one of theservers 214 ₁-214 _(P). Performance criteria (or performance rules) canbe configurable by an administrator (e.g., an owner, a lessee, or alessor) of the backend system 120.

In exemplary embodiment 200, data layer 240 can be configured in anactive replication topology wherein content (e.g., data and/or metadata)retained in a content storage site 250 _(μ) is replicated to each of theremaining content storage sites {250 _(μ′)}), with μ′=1, 2 . . . Q andμ′≠μ. In one aspect, replication of data can result in replicationlatency T_(νμ), or relative lag time of content storage site 250 _(μ) (atarget node) to instantiate a content update performed at contentstorage site 250 _(ν) (e.g., a source node). Accordingly, for eachcontent storage site 250 _(ν) in data layer 240, a plurality ofreplication latencies {T_(νν′)}, with ν′=1, 2 . . . Q and ν′≠ν, can beestablished. It should be appreciated that T_(νμ) can be different fromT_(μν) because the relative lag of content storage site 250 _(μ) □(as atarget node □) to apply (at content storage site 250 _(μ)) a contentupdate effected at content storage site 250 _(ν) (as a source node □)can be different from the relative lag of content storage site 250 _(ν)(as a target node □) to apply (at content storage site 250 _(μ)) acontent update effected at content storage site 250 _(μ) (as a sourcenode □). In certain scenarios, replication latency can range from theorder of few seconds to the order of tens of minutes (e.g., 22 minutes,35 minutes). In such active configuration, each content storage site canbe referred to as a target node for service of a content query (e.g.,query 118). As illustrated, in view of such symmetry for a replicationlatency, each content storage site 250 _(γ), with γ=1, 2 . . . Q, cantransmit, via data and signaling pipe 254 _(γν), data indicative oflatency T_(γν) to each content storage site 250 _(ν), with ν≠γ. Inaddition, each content storage site 250 _(γ), with γ=1, 2 . . . Q, canreceive data indicative of latency T_(γν) from other content storagesite 250 _(ν), with ν≠γ. Accordingly, in one aspect, each contentstorage site γ can compose a data structure containing data indicativeof the relative lag time for instantiation of specific content withrespect to other content storage site 250 _(γ′). In one implementation,the data structure can be a two-dimensional matrix T of real numbers:

$\overset{\leftrightarrow}{T} = {\begin{bmatrix}0 & T_{12} & T_{13} & \ldots & T_{1\; \gamma} \\T_{21} & 0 & T_{23} & \ldots & T_{2\; \gamma} \\T_{31} & T_{32} & 0 & \ldots & T_{3\; \gamma} \\\vdots & \vdots & \vdots & 0 & \vdots \\T_{\gamma \; 1} & T_{\gamma \; 2} & T_{\gamma \; 3} & \ldots & 0\end{bmatrix}.}$

FIG. 4 illustrates an exemplary embodiment 400 in which Q=3, whereincontent storage sites 250 ₁, content storage site 250 ₂, and contentstorage site 250 ₃ exchange, via data and signaling pipes 254 ₁₂, 254₂₃, and 254 ₁₃, data indicative of replication latency T_(αβ), withα,β=1, 2, 3, and β>α. In an aspect, content storage site 250 ₁ canreceive data indicative of the replication latency T₂₃ among contentstorage sites 250 ₂ and 250 ₃. In another aspect, content storage site250 ₂ can receive data indicative of the replication latency T₁₃ amongcontent storage sites 250 ₁ and 250 ₃. In yet another aspect, contentstorage site 250 ₃ can receive data indicative of the replicationlatency T₁₂ among content storage sites 250 ₁ and 250 ₂. In anotheraspect, content storage site 250 ₁ can transmit (e.g., broadcast), tocontent storage sites 250 ₂ and 250 ₃, data indicative of thereplication latency of such site with respect to each of content storagesites 250 ₂ and 250 ₃—e.g., content storage site 250 ₁ can transmit dataindicative of T₁₂ and T₁₃ to content storage site 250 ₂ and 250 ₃. As anillustration, each content storage site 250 _(α) can retain thefollowing matrix t of replication latencies:

$\overset{\leftrightarrow}{t} = {\begin{bmatrix}0 & T_{12} & T_{13} \\T_{21} & 0 & T_{23} \\T_{31} & T_{32} & 0\end{bmatrix}.}$

As illustrated in FIG. 4 for Q=3, a content storage site 250K cancomprise a data manager unit κ 418 _(κ) (also referred to as a datamanager 418 _(κ)) which can have more components, and a data storage κ224 _(κ) that can include a plurality of data storage elements. In oneaspect, data storage κ 224 _(κ) can be configured (e.g., installed,tested, and accepted) in a mated pair configuration to provideredundancy and thus increase resilience to malfunction or other issuesthat might impact negatively the performance of the content storage site250 _(κ). The data manager 418 _(κ) can transmit and receive dataindicative of replication latency in accordance with aspects describedherein. In addition or in the alternative, the data manager 418 _(κ) cangenerate a data structure having at least a portion of the received dataindicative of replication latency. For instance, the data manager 418_(κ) can compose a symmetric two-dimensional matrix (e.g., T) having arank equal to Q. The data manager 418 _(κ) can retain the data structurecan be retained in the data storage κ 224 _(κ).

A content storage site 250 _(κ) can acquire data indicative ofreplication latency T_(κκ′), with κ′=1, 2 . . . Q and κ′≠κ, according tovarious modalities. In one modality, the content storage site 250 _(κ),via data manager 418 _(κ), for example, can transmit a signaling beat toeach content storage site 250 _(κ′) in the replication topology of datalayer 240. The signaling beat can be a periodic control signal, such asa lightweight (e.g., 1-3 bit) control packet. Control signaling otherthan a signaling beat also can be utilized. In response to the signalingbeat, the content storage site 250 _(κ) can receive data indicative ofT_(κκ′) from at least one content storage site 250 _(κ′) in theplurality of content storage sites 250 ₁-250 _(Q). Upon or after suchdata is received, the content storage site 250 _(κ) can compose a datastructure having the data indicative of T_(κκ′) for content storagesites that supplied replication latency data in response to thesignaling beat. In another modality, the content storage site 250 _(κ)can subscribe to a utility application (e.g., a demon) executed by oneor more content storage sites of the plurality of content storage sites250 ₁-250 _(Q), the utility application transmitting data indicative ofreplication latency among the content storage site executing theapplication and the content storage site 250 _(κ) in response to anupdated (e.g., new) replication latency being determined for specificcontent. In yet another modality, which can be referred to as a pushmodality, the content storage site 250 _(κ) can transmit data indicativeof replication latency T_(κκ′) at predetermined instants (e.g.,periodically with period τ, or according to a schedule) to one or more(e.g., each one) of the plurality of content storage sites 250 ₁-250_(Q).

Replication latency can be determined in response to specific content(e.g., data or metadata) being instantiated in the content store sites250 ₁-250 _(Q) in the data layer 240. As described herein, the contentstore sites 250 ₁-250 _(Q) can be configured in an active replicationtopology. Accordingly, content that is retained in the data layer 240 ispropagated (e.g., transmitted) via data and signaling pipes 254 _(νμ)(with ν,μ=1, 2 . . . Q) among content storage sites 250 ₁-250 _(Q). Amodality of content propagation can include a publisher-subscriberapproach in which each content storage site 250 _(ν) of the contentstorage sites 250 ₁-250 _(Q) can transmit (e.g., publish) content changevectors (or data structures indicative of content change(s)) to theother content storage site 250 _(μ), with μ=1, 2 . . . Q. In addition,each content storage site 250 _(ν) of the content storage sites 250₁-250 _(Q) can subscribe to receive content change vectors from othercontent storage sites. In one aspect, when content is instantiated in acontent storage site 250 _(κ), signaling can be transmitted to eachcontent storage site 250 _(κ′) in the plurality of content storage sites250 ₁-250 _(Q). The content storage site can transmit the signaling,which can comprise control instructions, control packets, clock signals,or the like. In one aspect, content instantiation can refer to memoryallocation for the content and the content and retention (e.g.,persistence) of the content in the allocated memory. In certainembodiments, the content can be instantiated in a data storage 414 _(κ),and a data manager 414 _(κ) can generate and transmit the signaling. Inresponse to transmission of the signaling, the content storage site 250_(κ) can trigger a timer (or a clock or any type of counter) τ_(κκ′) foreach content storage site 250 _(κ′). In addition or in the alternative,the signaling (e.g., a control instruction) can instruct each of thecontent storage sites 250 _(κ′) in the plurality of content storagesites 250 ₁-250 _(Q) to transmit an acknowledgement (ACK) signal to thecontent storage site 250 _(κ) after or when the content has beeninstantiated in the content storage site 250 _(κ′). In response toreception of an ACK signal from a content storage site 250 _(κ′), thecontent storage site 250 _(κ) can receive can stop a respective timerτ_(κκ′). The value of the timer can indicate the replication latencyT_(κκ′).

In connection with generation of a routing pathway, to configureautomatically a specific content storage site 250 _(ν) for servicing thequery 118 in response to a performance condition of a server 214 _(κ) inthe application layer 150, T&C manager 224 can acquire (receive,retrieve, or otherwise access) and utilize data indicative ofreplication latency for specific content at the content storage sites250 ₁-250 _(Q). The specific content can be substantially common to eachone of the content storage sites (or target nodes) 250 ₁-250 _(Q). TheT&C manager 224 can acquire the data indicative of replication latencyvia, at least in part, data and signaling pipe 230. In oneimplementation, T&C manager 224 can poll, via data and signaling pipe230, each of the content storage sites 250 ₁-250 _(Q) for a datastructure having data indicative of the plurality of relative lag timesfor instantiation of the specific content. The T&C manager 224 can polleach of the content storage sites 250 ₁-250 _(Q) in nearly real time orat scheduled instants. In addition or in the alternative, the T&Cmanager 224 can poll each of the content storage sites 250 ₁-250 _(Q) inresponse to a predetermined event. In addition or in the alternative,the T&C manager 224 can configure automatically a destination node(e.g., a server) for queries (e.g., service queries, content queries, orthe like) in accordance with one or more predetermined criteria forperformance of the destination node, such as a server of the one or moreservers 214 ₁-214 _(P). In one scenario, the T&C manager 224 canautomatically decommission a server in response to the server having aperformance condition (e.g., “At Risk”) indicating that server may beapproaching an operation state in which servicing queries no longer ispossible or efficient. The T&C manager 224 can automaticallyre-commission a decommissioned server in response to such serverrecovering an operation state having a performance condition (e.g.,“Satisfactory”) indicating that the decommissioned server can be servicequeries (e.g., content queries, service queries, or the like).

In one latency-based routing scenario in exemplary embodiment 200, afterreplication latency data is acquired, the T&C manager 224 can monitordata indicative of performance to service a query for specific content(or a content query) for each server of the plurality of servers 214₁-214 _(P) in application layer 150. In one implementation, as part ofthe monitoring, the T&C manager 224 can compare such data with a serviceperformance criterion (e.g., one or more thresholds for a keyperformance indicator (KPI)). In response to such performance failing tofulfill a criterion for acceptable performance (e.g., performance isbelow a threshold) for at least one server (e.g., server 214 ₂) of theplurality of servers 214 ₁-214 _(P) in application layer 150, the T&Cmanager 224 can select an alternative server (e.g., server 214 _(P-1))of such plurality to service the content query (e.g., query 118) basedat least on replication latency of a content storage site associatedwith the alternative server with respect to at least one content storagesite of the plurality of content storage sites 250 ₁-250 _(Q) in datalayer 240. As an example, the T&C manager 224 can select the alternativeserver having an associated content storage site with the lowestreplication latency with respect to a content storage site associatedwith an underperforming server, e.g., a server having a performancecondition that fails to meet a criterion for acceptable performance.More complex routing criteria can be employed. In one aspect, the T&Cmanager 224 can select an alternative server based on replicationlatency of a content storage site associated therewith and performancecondition of the alternative server. An alternative server having acontent storage site with low replication latency with respect to acontent storage site associated with the underperforming server may notbe selected when the performance condition of the alternative server is“At Risk” for underperformance. In such scenario, the T&C manager 224can identify another alternative server suitable for servicing a queryinitially directed to an underperforming server.

FIG. 5 is a block diagram of an exemplary embodiment 500 of a networknode 502 in accordance with one or more aspects of the disclosure. Thenetwork node 502 is an apparatus that can embody a functional element ofapplication layer 130 and a data layer of the one or more data layers160. For example, network node 502 can embody a server of the one ormore servers 214 ₁-214 _(P), or a data manager unit (e.g., data manager418 ₁) that can be part of a content storage site. An exemplaryembodiment of a server is illustrated with a computing device 602 shownin FIG. 6. In the illustrated embodiment, the network node 502 comprisesa group of one or more I/O interfaces 504, a group of one or moreprocessors 508, a memory 516, and a bus 512 that functionally couples(e.g., communicatively couples) two or more of the functional elementsof the network node 502 including the group of one or more processors508 to the memory 516. In scenarios in which operation of network node502 can be critical to network performance (e.g., performance ofapplication layer 130), such as in security-sensitive applications(e.g., banking services), the group of one or more processors 508 cancomprise a plurality of processors that can exploit concurrentcomputing.

Functionality of network node 502 can be configured by a group ofcomputer-executable instructions (e.g., programming code instructions orprogramming modules) that can be executed by at least one processor ofthe one or more processors 508. Generally, programming modules cancomprise computer code, routines, objects, components, data structures(e.g., metadata objects, data object, control objects), and so forth,that can be configured (e.g., coded or programmed) to perform aparticular action or implement particular abstract data types inresponse to execution by the at least one processor. For example, afirst group of computer-executable instructions can configure logicthat, in response to execution by the at least one processor, can enablethe network node 502 to operate as a server (an application server, aprovisioning server, an AAA server, a proxy server, a communicationmanagement server, etc.), a gateway node (a session border controller(SBC), a media gateway control function ((MGCF), etc.), or a datamanager unit which can be part of a data layer, such as a data layer ofthe one or more data layers 160.

Data and computer-accessible instructions, e.g., computer-readableinstructions and computer-executable instructions, associated withspecific functionality of the network node 502 can be retained in memory516. Such data and instructions can permit implementation, at least inpart, of the latency-based routing, and related load balancing, ofqueries in accordance with one or more aspects of the disclosure. In oneaspect, the computer-accessible instructions can embody any number ofprogramming code instructions or program modules that permit specificfunctionality. In the subject specification and annexed drawings, memoryelements are illustrated as discrete blocks, however, such memoryelements and related computer-accessible instructions (e.g.,computer-readable and computer-executable instructions), and data canreside at various times in different storage elements (registers, memorypages, files, databases, memory addresses, etc.; not shown) in memory516.

Data storage 520 can comprise a variety of data, metadata, or both,associated with latency-based routing, and relating load balancing, inaccordance with aspects described herein. As an illustration, in aconfiguration in which the network node 510 can embody a server (such ascomputing device 602 shown in FIG. 6), such server can include datastorage (e.g., data storage 620) having data indicative of replicationlatency among a content storage site associated with the server andother content storage sites in a data layer (e.g., data layer 240). Atthe server, such data can be retained, for example, in a memory element,referred to as latency data 622. In addition, such server (e.g.,computing device 602) also can include data indicative of performancemetric(s) of one or more servers or data, such as a SNMP OID, that canreference a memory element in data storage 620 having data indicative ofperformance metric(s) of one or more servers. As an example, a memoryelement referred to as performance metric 623 can contain such data. Asanother illustration, in a configuration in which the network node 150can embody a data manager unit (e.g., data manager 702 shown in FIG. 7),such data manager unit can include data storage (e.g., data storage 720)having data indicative of replication latency of a content storage sitecomprising the data manager 702 and other content storage sites in adata layer (e.g., data layer 240). The data storage in the data managerunit (e.g., data manager 702) also can include data indicative of timervalues for instantiation of content at various content storage sites.For example, such data associated with timer values can be retained in amemory element, referred to as cached data 723.

Memory 516 also can comprise one or more computer-executableinstruction(s) for implementation of specific functionality of thenetwork node 502 in connection with the dynamic provisioning ofcommunication resources described herein. Such computer-executableinstructions can be retained as a memory element labeled functionalityinstruction(s) 518. In one aspect, as described herein, functionalityinstruction(s) 518 can be stored as an implementation (e.g., a compiledinstance) of one or more computer-executable instructions that implementand thus provide at least the functionality of the methods describedherein. Functionality instruction(s) 518 also can be transmitted acrosssome form of computer readable media. It should be appreciate thatdifferent functionality instruction(s) can render physically alikenetwork nodes into functionally different components (e.g., a server anda data manager unit), with functional differences dictated by logic(e.g., computer-executable instructions and data) specific to each oneof such network nodes and defined by the functionality instruction(s)518. In an exemplary configuration in which the network node 502embodies a server (e.g., computing device 602), the functionalityinstruction(s) 518 can comprise or embody computer-accessibleinstructions that, in response to execution by a processor (e.g., aprocessor of the one or more processors 608), can permit the server(e.g., computing device 602) to evaluate performance condition(s) of theserver and retain a record of such condition(s) in memory (e.g., memory616). Such computer-accessible instructions can be retained in a memoryelement, referred to as performance monitoring instruction(s) 618. Inanother exemplary configuration in which the network node 502 embodies adata manager unit (e.g., data manager 702), the functionalityinstruction(s) 518 can comprise or embody computer-accessibleinstructions that, in response to execution by a processor, can permitthe server to acquire data indicative of replication latency among acontent storage site comprising the data manager unit and other contentstorage sites deployed in a data layer (e.g., data layer 240). Suchcomputer-accessible instructions of the data manager unit can beretained in a memory element, referred to as signaling beatinstruction(s) 618.

Memory 516 can be embodied in a variety of computer-readable media.Exemplary computer-readable media can be any available media that isaccessible by a processor in a computing device, such as one processorof the group of one or more processors 508, and comprises, for example,both volatile and non-volatile media, removable and non-removable media.As an example, computer-readable media can comprise “computer storagemedia,” or “computer-readable storage media,” and “communicationsmedia.” Such storage media can be non-transitory storage media.“Computer storage media” comprise volatile and non-volatile, removableand non-removable media implemented in any methods or technology forstorage of information such as computer readable instructions, datastructures, program modules, or other data. Exemplary computer storagemedia comprises, but is not limited to, RAM, ROM, EEPROM, flash memoryor other memory technology, CD-ROM, digital versatile disks (DVD) orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe utilized to store the desired information and which can be accessedby a computer or a processor therein or functionally coupled thereto.Memories such as memory 616 and memory 726 which arise from specificconfiguration of memory 516 also can be embodied in thecomputer-readable media that embodies memory 516.

Memory 516, and the various configurations thereof such as memory 616and memory 716, can comprise computer-readable non-transitory storagemedia in the form of volatile memory, such as random access memory(RAM), electrically erasable programmable read-only memory (EEPROM), andthe like, or non-volatile memory such as read only memory (ROM). In oneaspect, memory 516 can be partitioned into a system memory (not shown)that can contain data and/or programming modules that enable essentialoperation and control of the network node 502. Such program modules canbe implemented (e.g., compiled and stored) in memory element 522,referred to as operating system (OS) instruction(s) 522, whereas suchdata can be system data that is retained in memory element 524, referredto as system data storage 524. The OS instruction(s) 522 and system datastorage 524 can be immediately accessible to and/or are presentlyoperated on by at least one processor of the group of one or moreprocessors 508. The OS instruction(s) 522 can embody an operating systemfor the network node. Specific implementation of such OS can depend inpart on architectural complexity of the network node 502. Highercomplexity affords higher-level OSs. Example operating systems caninclude Unix, Linux, iOS, Windows operating system, and substantiallyany operating system for a computing device. In certain scenarios, theoperating system embodied in OS instruction(s) 522 can have differentlevels of complexity based on particular configuration of the networknode 502. For example, an operating system for a server (e.g., computingdevice 602) can be more complex than an operating system for a datamanager unit (e.g., data manager 702). In an exemplary configuration inwhich the network node 502 embodies a server (e.g., computing device602), the memory element 522 can be embodied or can comprise the memoryelement, referred to as OS instruction(s) 622. Similarly, in anotherexemplary configuration in which the network node 502 embodies a datamanager unit (e.g., data manager 702), the memory element 522 can beembodied or can comprise the memory element, referred to as OSinstruction(s) 622.

Memory 516 can comprise other removable/non-removable,volatile/non-volatile computer-readable non-transitory storage media. Asan example, memory 516 can include a mass storage unit (not shown) whichcan provide non-volatile storage of computer code, computer readableinstructions, data structures, program modules, and other data for thenetwork node 502. A specific implementation of such mass storage unit(not shown) can depend on desired form factor of the network node 502and space available for deployment thereof. For suitable form factorsand sizes of the network node 502, the mass storage unit (not shown) canbe a hard disk, a removable magnetic disk, a removable optical disk,magnetic cassettes or other magnetic storage devices, flash memorycards, CD-ROM, digital versatile disks (DVD) or other optical storage,random access memories (RAM), read only memories (ROM), electricallyerasable programmable read-only memory (EEPROM), or the like.

As illustrated, the network node 502 can comprise a functionalityspecific platform 510 which can include one or more components thepermit functionality of the network node 502. In one embodiment, acomponent of the one or more components can be a firmware componentwhich can have dedicated resources (e.g., a processor, software, etc.)to implement certain functions that support implementation of orimplement at least part of the functionality of the network node 502. Inanother embodiment, the functionality specific platform 510 can includeat least a portion of the one or more processors 508 which can bededicated to execution of a part or all of the functionalityinstruction(s) 518, thus relieving at least some of the computationalload from the one or more processors 508 for other operation of thenetwork node 502. In one exemplary configuration in which the networknode 502 is configured as a server (e.g., computing device 602), thefunctionality specific platform 510 can be embodied in or can comprise aperformance monitoring component 610. In another exemplary configurationin which the network node 502 is configured as a data manager unit(e.g., data manager 702), the functionality specific platform 510 can beembodied in or can comprise a control signal generator unit 710 (alsoreferred to as control signal generator 710).

Features of latency-based routing of queries (e.g., service queries,content queries), and associated load balancing, in accordance withaspects described herein, can be performed, at least in part, inresponse to execution of software components by a processor. Thesoftware components can include one or more implementations (e.g.,encoding) of functionality instruction(s) 518 and specificconfigurations such as performance monitoring instruction(s) orsignaling beat instruction(s) 718. In particular, yet not exclusively,to provide the specific functionality of network node 502, or specificconfigurations thereof such as computing device 602 or data manager 702,a processor of the one or more processors 508 in network node 502, orprocessor(s) 608 in computing device 602 or processor(s) 708 in datamanager 702, can execute at least a portion of the computer-accessibleinstructions in functionality instruction(s) 518, or particularconfiguration thereof such as performance monitoring instruction(s) 618or signaling beat instruction(s) 718.

In general, a processor of the group of one or more processors 508, orprocessor(s) 608 or processor(s) 708 depending on specificconfiguration, can refer to any computing processing unit or processingdevice comprising a single-core processor, a single-core processor withsoftware multithread execution capability, multi-core processors,multi-core processors with software multithread execution capability,multi-core processors with hardware multithread technology, parallelplatforms, and parallel platforms with distributed shared memory (e.g.,a cache). In addition or in the alternative, a processor of the group ofone or more processors 508 can refer to an integrated circuit withdedicated functionality, such as an application specific integratedcircuit (ASIC), a digital signal processor (DSP), a field programmablegate array (FPGA), a complex programmable logic device (CPLD), adiscrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.In one aspect, processors referred to herein can exploit nano-scalearchitectures such as, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage (e.g., improve formfactor) or enhance performance of the computing devices that canimplement the various aspects of the disclosure. In another aspect, theone or more processors 508 can be implemented as a combination ofcomputing processing units.

The one or more input/output (I/O) interfaces 504 can functionallycouple (e.g., communicatively couple) network node 502 to anotherfunctional element (component, unit, server, gateway node, repository,etc.) of core network platform 120 or distribution platform 130, forexample. Functionality of the network node 502 that is associated withdata I/O or signaling I/O can be accomplished in response to execution,by a processor of the group of one or more processors 508, of at leastone I/O interface retained in memory element 528. Such memory element isrepresented by the block I/O interface(s) 528. In some embodiments, theat least one I/O interface embodies an API that permit exchange of dataor signaling, or both, via an I/O interface of I/O interface(s) 504. Incertain embodiments, the one or more I/O interfaces 504 can include atleast one port that can permit connection of the network node 502 toother functional elements of the exemplary network environment 100. Inone or more scenarios, the at least one port can comprise networkadaptor(s) such as those present in reference links, and other networknodes. In other scenarios, the at least one port can include one or moreof a parallel port (e.g., GPIB, IEEE-1284), a serial port (e.g., RS-232,universal serial bus (USB), FireWire or IEEE-1394), an Ethernet port, aV.35 port, or the like. The at least one I/O interface of the one ormore I/O interfaces 504 can enable delivery of output (e.g., outputdata, output signaling) to such functional elements. Such output canrepresent an outcome or a specific action of one or more actionsdescribed herein, such as in the methods of FIG. 8 and FIGS. 9A-9B.Specific configurations, or deployments, of the one or more I/Ointerfaces 504, such as I/O interface(s) 604 in the computing device 602or I/O interface(s) 704 in the data manager 702, can include at leastone feature of the one or more I/O interface(s) 504.

Bus 512, and the various configurations thereof, such as bus 612 and bus712, represents one or more of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. As an example, such architectures cancomprise an Industry Standard Architecture (ISA) bus, a Micro ChannelArchitecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video ElectronicsStandards Association (VESA) local bus, an Accelerated Graphics Port(AGP) bus, and a Peripheral Component Interconnects (PCI), a PCI-Expressbus, a Personal Computer Memory Card Industry Association (PCMCIA),Universal Serial Bus (USB), and the like.

In view of the various aspects of routing of service queries fordata/content in a data/content repository with distributed replicationtopology, such as those described herein, exemplary methods that can beimplemented in accordance with the disclosure can be better appreciatedwith reference to the exemplary flowcharts in FIG. 8 and FIGS. 9A-9B.For simplicity of explanation, the exemplary methods disclosed hereinare presented and described as a series of actions (also referred to assteps), pictorially represented with a block. However, it is to beunderstood and appreciated that implementation, and related advantages,of such methods is not limited by the order of actions, as some actionsmay occur in different orders and/or concurrently with other actionsfrom that shown and described herein. For example, the various methods(also referred to as processes) of the disclosure can be alternativelyrepresented as a series of interrelated states or events, such as in astate diagram. Moreover, when disparate functional elements (networknodes, units, etc.) implement different portions of the methods of thedisclosure, an interaction diagram or a call flow can represent suchmethods or processes. Furthermore, not all illustrated actions may berequired to implement a method in accordance with the subjectdisclosure.

The methods disclosed throughout the subject specification and annexeddrawings can be stored on an article of manufacture, orcomputer-readable storage medium, to facilitate transporting andtransferring such methods to computing devices (e.g., desktop computers,mobile computers, mobile telephones, and the like) for execution, andthus implementation, by a processor or for storage in a memory.

FIG. 8 is a flowchart of exemplary method 800 for latency-based routingof service requests in a content repository in accordance with at leastcertain aspects of the disclosure. As described herein, the data/contentrepository can be deployed in an active replication topology (see, e.g.,FIG. 2). The exemplary method 800 can be implemented (e.g., performed orexecuted) by a network node, such as the T&C manager 224, or a processortherein or functionally coupled thereto. At block 810, data indicativeof a plurality of relative lag times for instantiation of content (e.g.,specific data or specific metadata) at a first plurality of networknodes is received. The first plurality of network nodes can be deployedin a first layer, such as a data layer (e.g., one of the content storagesites 250 ₁-250 _(Q), or a data manager therein). Such data can bereceived at the network node that implements the subject exemplarymethod. In one aspect, the content can be substantially common to eachnetwork node of the first plurality of network nodes. In another aspecteach of the network nodes of the first plurality of nodes can be atarget node in a data replication topology. Block 810 can be referred toas the receiving action and can comprise polling each one of the firstplurality of network nodes for a data structure indicative of theplurality of relative lag times for instantiation of the content. Here,in one aspect, polling includes submitting a request for certain data toa network element (a server, a unit, a device, etc.) and receiving aresponse, from the network element, the response including the requesteddata. At block 820, performance to service a query for the content (orservice performance for the query) is monitored, or otherwise evaluated,for each network node of a second plurality of network nodes (e.g.,servers 214 ₁-214 _(P)). The second plurality of network nodes can bedeployed in a second layer, such as an application layer (e.g.,application layer 150). At block 830, in response to such performance(also referred to as service performance) of a first network nodefulfilling a balancing criterion (e.g., having certain value for a keyperformance indicator (KPI) below threshold), a second network node ofthe first plurality of network nodes in the first layer can beconfigured to service the query for the content based at least on arelative lag time of the second network node with respect to at leastone third network node of the first plurality of network nodes. In oneaspect, block 830 can be referred to as the configuring action and cancomprise redirecting the query for the specific content to the secondnetwork node.

In a scenario in which the service performance for the query does notfulfill the balancing criterion, flow can be directed to block 820 tocontinue evaluating such service performance. In one implementation,flow of the exemplary method 800 can be redirected to block 810according to a monitoring protocol to evaluate the service performance,e.g., specific time dependence for implementation of block 820. Suchtime dependence can establish, at least in part, a nearly-continuousmonitoring or a schedule-based monitoring. Event-based monitoring of theservice performance of the query also can be implemented.

In certain embodiments, the exemplary method 800 also can includestep(s) (not shown) at which an object identifier indicative of theperformance to service the query is provided, by each one of theplurality of network nodes in the application layer, for each networknode of the plurality of network nodes in the application layer.

FIGS. 9A-9B are flowcharts of exemplary methods for generatinginformation related to replication latency in accordance with at leastcertain aspects of the disclosure. As described herein, such informationcan be utilized for routing service requests in a data/contentrepository having an active replication topology. The exemplary methods900 and 950 can be implemented (e.g., performed or executed) by anetwork node, such as a data manager that is part of a content storagesite of the group of content storage sites 250 ₁-250 _(Q), or aprocessor therein or functionally coupled thereto. Regarding exemplarymethod 900, at block 910, control signaling, such as a signaling beat,among a first network node (e.g., data manager 418 ₂) and a plurality ofnetwork nodes is provided, the first network node and the plurality ofnetwork nodes can be configured in a data replication topology. The datareplication topology can be deployed in a data layer. The signaling beatcan be a periodic control signal as described herein. At block 920, dataindicative of a plurality of relative replication latencies forinstantiation of specific data at a plurality of network nodes isreceived in response to the signaling beat. At block 930, a datastructure having data indicative of such plurality of relativereplication latencies is composed or otherwise generated. The subjectblock can be referred to as the composing action and can comprisegenerating an off-diagonal (symmetric or non-symmetric) matrix havingmatrix elements indicative of relative replication latency among a firstnetwork node (e.g., data manager 418 ₁) of the plurality of networknodes (e.g., data managers 418 ₁-418 _(Q) of content storage sites 250₁-250 _(Q)) and a second network node (e.g., data manager 418 _(Q)) ofthe plurality of network nodes.

Regarding exemplary method 950, blocks 960-980 are similar to blocks910-930, respectively and thus can be implemented in a similar manner.At block 990, data associated with each replication latency in the datastructure is supplied. Block 990 can be implemented in various manners.In one aspect, at block 990 a, each replication latency in the datastructure can be transmitted to each one of the plurality of networknodes (e.g., data managers 418 ₁-418 _(Q) of content storage sites 250₁-250 _(Q)). In another aspect, at block 990 b, each replication latencyin the data structure can be transmitted to a network node of anapplication layer. In yet another aspect, at block 990 c, dataindicative of replication latency is transmitted to a network node ofthe plurality of network nodes in response to receiving the signalingbeat. In certain scenarios, implementation of block 990 can compriseimplementation of any two of the blocks 990 a through 990 c. In otherscenarios, all three blocks 990 a-990 c can be implemented.

When compared with conventional technologies for routing traffic orqueries to a distributed content repository, various advantages of thedisclosure over such technologies emerge from the subject specification.For example, the disclosure can provide routing criteria based at leaston relative replication latency and performance conditions, and permitautomated determination of routing pathways for content queries and,more generally, traffic.

One or more embodiments of the subject disclosure can employ artificialintelligence (AI) techniques such as machine learning and iterativelearning. Examples of such techniques include, but are not limited to,expert systems, case based reasoning, Bayesian networks, behavior basedAI, neural networks, fuzzy systems, evolutionary computation (e.g.genetic algorithms), swarm intelligence (e.g. ant algorithms), andhybrid intelligent systems (e.g. expert inference rules generatedthrough a neural network or production rules from statistical learning).

While the systems, apparatuses, and methods have been described inconnection with exemplary embodiments and specific examples, it is notintended that the scope be limited to the particular embodiments setforth, as the embodiments herein are intended in all respects to beillustrative rather than restrictive.

Unless otherwise expressly stated, it is in no way intended that anyprotocol, procedure, process, or method set forth herein be construed asrequiring that its acts or steps be performed in a specific order.Accordingly, in the subject specification, where a description of aprotocol, procedure, process, or method does not actually recite anorder to be followed by its acts or steps or it is not otherwisespecifically stated in the claims or descriptions that the steps are tobe limited to a specific order, it is no way intended that an order beinferred, in any respect. This holds for any possible non-express basisfor interpretation, including: matters of logic with respect toarrangement of steps or operational flow; plain meaning derived fromgrammatical organization or punctuation; the number or type ofembodiments described in the specification or annexed drawings, or thelike.

It will be apparent that various modifications and variations can bemade without departing from the scope or spirit of the subjectdisclosure. Other embodiments will be apparent from consideration of thespecification and practice disclosed herein. It is intended that thespecification and examples be considered as non-limiting illustrationsonly, with a true scope and spirit of the subject disclosure beingindicated by the following claims.

What is claimed is:
 1. A method comprising: receiving, at a firstnetwork node, data indicative of a plurality of relative lag times forinstantiation of a specific content item at a first plurality of networknodes, the specific content item being common for each network node ofthe first plurality of network nodes; receiving, at the first networknode, network performance data related to servicing a request for thespecific content item for each network node of a second plurality ofnetwork nodes; receiving a request for the specific content item from atleast one network node of the second plurality of network nodes;selecting a second network node of the second plurality of network nodesto service the request for the specific content item, the second networknode of the second plurality of network nodes being configured based atleast on the network performance data and a lag time for instantiationof the specific content item at a network node of the first plurality ofnetwork nodes associated with the second network node of the secondplurality of network nodes; and causing the second network node of thesecond plurality of network nodes to service the request.